Split release into two workflows #143
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gastaldi
force-pushed
the
split_release
branch
from
867a9fe to
0412841
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This splits the release workflow into two separate workflows.
The
release-perform.ymlis triggered when a tag is pushed or can also be invoked manually (for cases where central isn't behaving properly and a retry may be necessary).Note that you can already retry failed steps in the existing release.yml workflow, however it will use the same SHAs for the reusable workflows, meaning that if the workflow has a bug and needs to change, you can't rely on the "Retry Failed Jobs".